|
|
Hi YK, I have checked in the DTS that the UnifyKey setup is secure. ./common/arch/arm64/boot/dts/amlogic/g12a_s905x2_eagle_3g.dts line: 494, 527, 542 TEE: When key-device is set to secure, these keys are likely stored in the TEE REE: When key-device is set to normal or another non-secure setting, these keys are typically stored in the REE. The case of your question (HDCP/widevien/playready) are all set to secure. BR, Kinbay |
|
|
Hi Kinbay To briefly what you're saying STB uses UnifyKey, but some of the key(HDCP/widevien/playready) use TEE Is it correct? one more thing , do you know what the files below are ? console:/vendor/lib/teetz # ls -la total 2532 drwxr-xr-x 2 root shell 4096 2009-01-01 09:00 . drwxr-xr-x 10 root shell 12288 2009-01-01 09:00 .. -rw-r--r-- 1 root root 129040 2009-01-01 09:00 00d1ca22-1764-4e35-90aa-5b8c12630764.ta -rw-r--r-- 1 root root 170616 2009-01-01 09:00 2c1a33c0-44cc-11e5-bc3b-0002a5d5c51b.ta -rw-r--r-- 1 root root 131540 2009-01-01 09:00 526fc4fc-7ee6-4a12-96e3-83da9565bce8.ta -rw-r--r-- 1 root root 927080 2009-01-01 09:00 8efb1e1c-37e5-4326-a5d6-8c33726c7d57.ta -rw-r--r-- 1 root root 454316 2009-01-01 09:00 9a04f079-9840-4286-ab92-e65be0885f95.ta -rw-r--r-- 1 root root 688156 2009-01-01 09:00 e043cde0-61d0-11e5-9c26-0002a5d5c51b.ta -rw-r--r-- 1 root root 346044 2009-01-01 09:00 e043cde0-61d0-11e5-9c260002a5d5c5ca.ta -rw-r--r-- 1 root root 134340 2009-01-01 09:00 e92a43ab-b4c8-4450-aa12-b1516259613b.ta -rw-r--r-- 1 root root 129076 2009-01-01 09:00 ff2a4bea-ef6d-11e6-89cc-d4ae52a7b3b3.ta Thank you YK.Jung image.png (26,118 bytes) |
|
|
Hi YK, About the TEE document, you can find it in ./common/Documentation/tee.txt You can find the ta files under vendor/amlogic/common/ BR, Kinbay |
|
|
Hi Kinbay Thank you for feedback.. One more thing In the case of Smart3, the Unifykey / REE method is used from ATV9. It's maintained until now ( ATV12.) Please check whether the current status is in violation of Google ATV12's policy or rules. It would be better to have Google data(link) related to it Please check it Thank you YK.Jung |
|
|
Hi Kinbay 1) About #c16586 >> Please check whether the current status is in violation of Google ATV12's policy or rules. Please contact Taiwan's SoC or find Google Docs ( link.. ) 2) Where are the keys stored in the EMMC memory map? 3) Can I access the keys directly by using console / adb? I have to report the above 3 contents to SKB by tomorrow. Please check it and if there is anything confirmed above, please update it Thank you YK.Jung |
|
|
Hi Kinbay 1) About #c16586 >> Please check whether the current status is in violation of Google ATV12's policy or rules. >> Please contact Taiwan's SoC or find Google Docs ( link.. ) ==> Please update it as soon as it is confirmed. 2) Where are the keys stored in the EMMC memory map? ==> I dont' think it will take log to check this , so please check it quickly SKB is complaining 3) Can I access the keys directly by using console / adb? ==> The answer to this to SKB is ready Please ignore this confirmation Thank you YK.Jung |
|
|
Hi YK, => Please check whether the current status is in violation of Google ATV12's policy or rules. ==> We checked with Amlogic, and they don't have the documents. => Where are the keys stored in the EMMC memory map? ==> I think it is in the tee part as shown below. --- Partition Map for MMC device 1 -- Partition Type: AML Part Start Sect x Size Type name 00 0 8192 512 U-Boot bootloader 01 73728 131072 512 U-Boot reserved 02 221184 2211840 512 U-Boot cache 03 2449408 16384 512 U-Boot env 04 2482176 16384 512 U-Boot logo 05 2514944 49152 512 U-Boot recovery 06 2580480 16384 512 U-Boot misc 07 2613248 16384 512 U-Boot dtbo 08 2646016 16384 512 U-Boot cri_data 09 2678784 32768 512 U-Boot param 10 2727936 32768 512 U-Boot boot 11 2777088 32768 512 U-Boot rsv 12 2826240 32768 512 U-Boot metadata 13 2875392 4096 512 U-Boot vbmeta 14 2895872 65536 512 U-Boot tee 15 2977792 16384 512 U-Boot factory 16 3010560 3313664 512 U-Boot super 17 6340608 32768 512 U-Boot factory_setting 18 6389760 204800 512 U-Boot btv_home 19 6610944 8658944 512 U-Boot data --- BR, Kinbay |
|
|
Hi Kinbay Thank you for update I will report to SKB with the above and update you if there is any further confirmation from SKB. Thank you YK.Jung |
|
|
Hi Kinbay >> Please check whether the current status is in violation of Google ATV12's policy or rules. >>>> We checked with Amlogic, and they don't have the documents. then is there any official feedback from Amlogic that the current status(using Unifykey method at OS12) is ok? If you have any official feedback, please share it with us. Can FXN contact 3PL for an official answer about this? I'm not sure if it's better to check with 3PL or not. Please give us your opinion. Thank you YK.Jung |
|
|
Hi YK, Amlogic Taiwan FAE said they aleady asked their Korea FAE to explain to SKB. If ALT need to know details, ALT can check with Amlogic Korea FAE. Thanks! |
|
|
no activity for this issue |
- yk.jung ( (ALTech) Younkwang Jung ) developer
.png)
